Repository navigation
Conversation
After that date the WordPress release announcement job gets 410 Gone from GitHub when it checks for or creates the wordpress@ release, so releases stop being recorded. This sends X-GitHub-Api-Version 2026-03-10 from the one shared githubRequest helper; the code only reads the response status and posts fields that the listed 2026-03-10 breaking changes do not touch.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
After that date the WordPress release announcement job gets 410 Gone from GitHub when it checks for or creates the wordpress@ release, so releases stop being recorded.
X-GitHub-Api-Version 2022-11-28 stops working (takes effect on 10 Mar 2028, source).
Fix
This sends X-GitHub-Api-Version 2026-03-10 from the one shared githubRequest helper; the code only reads the response status and posts fields that the listed 2026-03-10 breaking changes do not touch.
scripts/announce-wordpress-release.mjs:85scripts/announce-wordpress-release.mjs:99scripts/announce-wordpress-release.mjs:110scripts/announce-wordpress-release.mjs:169scripts/announce-wordpress-release.mjs:186How I checked
The calls now follow Github's announcement.
node --test scripts/announce-wordpress-release.test.mjspasses.Not checked
The breaking-changes list was only partly readable and I could not call the API, so I checked by reading that the releases endpoints are not named in the visible entries.
Okapi is an API watcher: it prevents API breaking changes by opening pull requests like this one.